What this PR does / why we need it:

I noticed when invoking make test-integration in k/k with KUBE_TEST_VMODULE="dynamicresources=5" that I never saw logs at that level in dynamicresources.go even when KUBE_TEST_VMODULE="*=5" did show them. Copilot identified a bug here as the cause. I confirmed that by setting vmodule to logr=5 and then saw logs from all files at that verbosity.

At least in the test, the info.CallDepth given to us by logr is 1, and adding that extra frame goes from logr.go to testinglogger_test.go where the logger is invoked:

0  0x0000000000609236 in k8s.io/klog/v2/ktesting.tlogger.Enabled
   at ./ktesting/testinglogger.go:310
1  0x000000000060ab3c in k8s.io/klog/v2/ktesting.(*tlogger).Enabled
   at <autogenerated>:1
2  0x00000000005f09e7 in github.com/go-logr/logr.Logger.Info
   at /home/jon/go/pkg/mod/github.com/go-logr/logr@v1.4.1/logr.go:276
3  0x000000000060fe65 in k8s.io/klog/v2/ktesting_test.TestCallDepth
   at ./ktesting/testinglogger_test.go:150
4  0x000000000055292e in testing.tRunner
   at /usr/lib/go/src/testing/testing.go:2036
5  0x00000000005547aa in testing.(*T).Run.gowrap1
   at /usr/lib/go/src/testing/testing.go:2101
6  0x0000000000497da1 in runtime.goexit
   at /usr/lib/go/src/runtime/asm_amd64.s:1771

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

I took over the existing TestCallDepth for a new test here since that didn't seem to be doing anything interesting.

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

Fixed a bug where the `-vmodule` flag hooked into the ktesting logger only ever matched against the "logr" module.